home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software Vault: The Diamond Collection
/
The Diamond Collection (Software Vault)(Digital Impact).ISO
/
cdr14
/
dv_wchlp.zip
/
DV&WCHLP.DOC
next >
Wrap
Text File
|
1995-03-17
|
52KB
|
1,182 lines
Desqview 2.6x & High Speed Communications
-----------------------------------------
Table of Contents
Topic Section
----- -------
Preamble ....................................... 1.0
Target Audience ................................ 1.1
Doucment History ............................... 1.2
Desqview and High Speed Communications ......... 2.0
Desqview Beyond COM1 & COM2 .................... 2.1
Desqview Factory Default Settings .............. 2.2
Desqview Related Key DOS Level Settings ........ 2.3
QEMM Exception Errors #6,#13 etc ............... 2.4
Desqview Settings .............................. 2.5
Desqview & Shared Interrupts ................... 2.6
Desqview & Port Addressess ..................... 2.7
Desqview Windows using Serial Ports ............ 2.8
FIFO Transmit and Receive Buffers .............. 3.0
16450 vs 16550A UARTS .......................... 4.0
Hayes ESP Card ................................. 5.0
Desqview & Hayes ESP Card ...................... 5.1
DTE Locked Baud Rates .......................... 6.0
Modem Profiles NRAM ............................ 7.0
Wildcat Multi-Line Setup ....................... 8.0
Wildcat Multi-Line Setup Batch Files ........... 8.1
Wildcat .MDM File Settings ..................... 8.2
Wildcat Upload and Download Failures............ 9.0
Poor Quality Phone Lines........................ 9.1
File Transfer Failure Hardware Factors.......... 9.2
File Transfer Failure Software Factors.......... 9.3
Summary ........................................ 10.0
Contacting the Author .......................... 11.0
1.0 - Preamble
--------------
This paper focuses on Desqview, Qemm, BBS Software, Hayes V.FAST Modems and
the ESP technolgy
It should be noted from the outset that Quarterdeck Office Systems, the OEM
of Desqview, have produced some very helpful .TEC documents which can be
found on CIS, Quarterdecks BBS or my Host BBS.
I have no formal association with the OEM mentioned below and enphasize
that the material that follows reflects my own personal view and
experience.
1.1 - Target Audience
---------------------
Both BBS operators and terminal emulation users will benefit from the
information in this document.
Desqview is used as the multi-tasker for the following BBS Packages:
GAP REMOTEACCESS TINYHOST WWIV
MEGAHOST ROBOBOARD/FX TRIBBS
OPUS-CBCS SEARCHLIGHT ULTRABBS
PCBOARD SPITFIRE VIRTUAL BBS
POWERBOARD SYNCRONET WILDCAT
1.2 - Document History
----------------------
Jan 1995 - v1.0 - First Public Release
v1.1 - Added Contents
- Added Multi-Line Help
- Added QEMM Exception Info
Feb 1995 - v1.2 - Minor changes to document
March 1995 - v1.3 - Began adding Help on File Transfer
Failures
- File renamed from DV&WCV10.TXT to
DV&WCHLP.ZIP
2.0 - Can Desqview Handle High Speed Serial Communications?
-----------------------------------------------------------
Yes!. Despite the fact that the Desqview manual only mentions 2400 to 9600
bps and implies that 9600 bps is HIGH SPEED, Desqview is able to handle the
new V.FAST Class modems at full throughput.
2.1 - Can Desqview Address more than COM1 and COM2?
---------------------------------------------------
Yes!. The Desqview documentation mentions COM1 & COM2 but omits to mentions
COM3 onwards. Nevertheless any Desqview window can use the full range of
COM1 to COM8. Desqview also indirectly supports FOSSIL drivers.
2.2 - Are the Desqview 'Factory Default' settings suitable for High Speed Links?
--------------------------------------------------------------------------------
No!. A lot of people have literally given up on Desqview because they do
not have the patience to configure their DOS/Desqview environment to work
with programs that use Serial Ports.
2.3 - What are the Key Settings - DOS Level
---------------------------------------------
Firstly, I stronly recommend you use QEMM and not the DOS HIMEM.SYS and
EMM386.EXE drivers.
A typical DOS/QEMM CONFIG.SYS file might look like this in a STANDARD UART
environment with 1 to 4 Modem Lines.
CONFIG.SYS
----------
DEVICE = C:\QEMM\DOSDATA.SYS
(1) DEVICE = C:\QEMM\QEMM386.SYS R:2 RAM
(2) DEVICE = C:\QEMM\DOS-UP.SYS @C:\QEMM\DOS-UP.DAT
DOS = HIGH
FILES = 80
(3) BUFFERS = 30
(4) STACKS = 0,0
COUNTRY = 061,437 C:\DOS\COUNTRY.SYS
LASTDRIVE = H
(5) SHELL = C:\QEMM\LOADHI.COM /R:2 \DOS\COMMAND.COM C:\DOS\ /E:2048 /p
A typical DOS/QEMM AUTOEXEC.BAT file might look like this in a STANDARD UART
environment with 1 to 4 Modem Lines.
AUTOEXEC.BAT
------------
@ECHO OFF
PROMPT=$P$G
(6) PATH=D:\;C:\WC4;\DV;C:\;\DOS;\NU;\QEMM;
\NU\IMAGE C:
CLS
(7) SHARE /F:5120 /L:80
(8) \ESP\ESPCA P280:1 R280:+ P288:1 R288:+ F
(9) \NU\NCACHE2 C: /EXP=4120 /BLOCK=8192 /QUICK=OFF /-I /WRITE=0
Notes:
(1) The QEMM386.SYS parameters are explained clearly in the QEMM Guide so
I will not touch on them here.
(2) A handy HINT is to backup all of the QEMM semi-dynamic data files to
avoid lenghty crash recover delays.
(4) A lot of programs insert a STACKS 9,256 statement in your CONFIG.SYS
file this is of NO value to Desqview which automatically uallocates stack
space when requested by programs.
(5) A number of Communications programs use DOS environment space for SET
commands such as SET IRQID= if insufficent environment space is
available you will loose these commands from the DOS environment table
which may stop your programs from working. So make sure set aside
extra environment space if using lots of DOS variables
(6) Program peformance is can be significantly improved if you optimise
your PATH= statement. Frequently use programs should reside on
directory's closest to the = sign.
(7) DO NOT load SHARE.EXE High or in your CONFIG.SYS file as an INSTALL
= command. SHARE will not function correctly in HIGH memory.
(8) If you using the HAYES ESP card, then configure the card on a single
line, for some reason invoking the program twice on some PC's causes
lock-ups. (See the ESP Section for More Info)
(9) Many users have reported problems with file transfers when using the
SMARTDRV program. If you ensist on using SMARTDRV then use
SMARTDRV /X
to TURN OFF write behind caching. I have found the Nortons NCACHE2
program to be a better DISK cache for use in the COMMS environment.
You may be able to get away with usingd delayed writes using NCACHE2.
If so the command line would be something like this:
\NU\NCACHE2 C: /EXP=4120 /BLOCK=8192 /MULTI=ON /WRITE=24
The main thing to remember about cache programs is that they can be
guilty of grabing software interrupts at just the WRONG time.
A typical DOS/QEMM CONFIG.SYS file might look like this in a DIGIBOARD or
FOSSIL driver environment with 1 to 8 Modem Lines.
DEVICE = C:\QEMM\DOSDATA.SYS
(10) DEVICE = C:\QEMM\QEMM386.SYS X=D000-DFFF RAM ST:M R:2
DEVICE = C:\QEMM\DOS-UP.SYS @C:\QEMM\DOS-UP.DAT
DOS = HIGH
FILES = 200
BUFFERS = 8
STACKS = 0,0
COUNTRY = 061,437 C:\DOS\COUNTRY.SYS
SHELL = C:\QEMM\LOADHI.COM /R:3 /RES=4800 /SQT=D000-DAFF C:\COMMAND.COM /E:2048 /P
LASTDRIVE = Z
(11) DEVICE = C:\DIGI\DOS\XIDOS5.SYS
Notes:
(10) In the DigiBoard environment its is important to EXCLUDE the memory being
used by the Digiboards XIDOS5.SYS driver.
(11) Take Note that the Digiboard driver is Loaded LOW not high. You will
experience problems if you load the driver HIGH.
2.4 - QEMM - Exception Errors
-----------------------------
One of the first problems that you may encounter when setting up your
system at the DOS Level is QEMM Exception Errors, typically #13.
The following .TEC Document Text from Quarterdeck may help!
QUARTERDECK QUARTERDECK QUARTERDECK QUARTERDECK QUARTERDECK QUARTERDECK
-----------------------------------------------------------------------
ID:X3 Troubleshooting Exception #6, #12, and #13 Errors
Quarterdeck Technical Note #232
Subject: Detailed explanation and troubleshooting procedures for
Exception #6, #12, and #13 error messages and system lockups.
OVERVIEW
--------
This document addresses Exception #6, #12 and #13 error messages. These
three Exceptions are so similar in cause, nature, and solution that they
will all be covered by the information below. Any reference to an
Exception error in this document applies to an Exception #6, Exception
#12, or Exception #13 error.
Please note that sometimes QEMM cannot report the error to the screen, so
a blank screen or a lockup occurs. For troubleshooting purposes, treat a
system lockup or a blank screen (that accepts no input) to be the same as
an Exception error.
This troubleshooting procedure will isolate and resolve the conflict most
effectively if you are able to reproduce the conflict at will (i.e., you
know of a specific action or series of actions that will cause the
conflict to occur). The reason for this is that this procedure follows a
logical set of tests to determine when a conflict is occuring and when it
is not. A conflict that randomly occurs is difficult to troubleshoot
because you do not know for sure when the configuration being used is
actually resolving the conflict.
Q: What is an Exception error?
A: An Exception #13 is the most common exception error reported by QEMM.
It is an error generated by the PC's processor notifying you that an
invalid instruction has been issued. The invalid instruction may
have come directly from software running on your machine, the result
of a conflict between software and hardware, or a conflict between
two hardware devices.
An Exception #12 is caused by the stack boundary being crossed. This
Exception can often be generated by an Exception #13.
An Exception #6 is an invalid opcode resulting from the CPU's
instruction pointer being pointed at a value that is not a valid
operation or instruction for the CPU.
An Exception error is not generated by QEMM, but by your PC's
processor. QEMM has the ability to detect these errors and display
them to the screen. The error message informs you what has happened
so that you may take the necessary steps to resolve the conflict.
Without QEMM's warning, your system would have simply crashed or hung
without an error message, or would have become unstable. For more
detailed information about the error messages themselves, please
refer to Technical Note #142, "QEMM-386: Exception 13 Explained"
(EXCEPT13.TEC).
Q: How do I resolve my Exception error?
A: Follow these steps:
DETERMINING YOUR QEMM VERSION
-----------------------------
Before beginning this troubleshooting guide, you must first ensure that
you have QEMM 7 installed. Previous QEMM versions do not apply to this
flowchart. To determine the version of QEMM that is installed on your
computer, type QEMMREG from the \QEMM directory.
??? If the version of QEMM is not 7, you should upgrade to ensure
complete compatibility with all of the current hardware and software
on the market. Since new hardware and software is released
regularly by other vendors, QEMM is constantly being updated to
perform optimally and without conflict with the latest hardware and
software products on the market. QEMM is also updated to work
around flaws in other products to ensure system stability. The
APPENDIX at the end of this technical note contains details about
updating QEMM.
??? If the QEMM version is 7.01, you should obtain an update to the
latest version of QEMM to avoid any potential conflicts. Even if
your QEMM version is later than 7.01, updating to the latest QEMM
version is advised. The APPENDIX at the end of this technical note
contains details about updating QEMM.
With version 7.02 or later, please continue.
STEP 1
TAMING DOWN QEMM
----------------
*STEALTH*
Run the QSETUP program from the \QEMM directory, select P, "Review or
change QEMM parameters," and examine your DEVICE=QEMM386.SYS line. If
you do NOT see an ST:M or ST:F anywhere on that line, proceed to the next
section, *TROUBLESHOOTING MODE*.
If you DO see an ST:M or ST:F, select S, "Stealth ROMs," then O to turn
Stealth off. Pressing <Enter> will bring you back to the "Review or
change QEMM parameters" screen, where you should press "A" to accept the
changes, followed by "S" to save the changes. At this point you should
reboot the machine and try to recreate the Exception error.
??? IF THE EXCEPTION ERROR DOES NOT OCCUR: QEMM's Stealth ROM feature
is involved with the Exception error on your system. You should
follow the STEALTH.TEC technote in the \QEMM\TECHNOTE directory to
configure Stealth to avoid the conflict. You are finished with this
technote.
??? IF THE EXCEPTION ERROR STILL OCCURS: Continue with the next section,
*TROUBLESHOOTING MODE*.
*TROUBLESHOOTING MODE*
Run the QSETUP program from the \QEMM directory, select P, "Review or change
QEMM parameters," press <Page Down> twice, and select "Set up QEMM for
troubleshooting." This will add several troubleshooting parameters to the
QEMM386.SYS device line for you. Pressing <Enter> will bring you back to
the "Review or change QEMM parameters" screen, where you should press "A"
to accept the changes, followed by "S" to save the changes.
Reboot the machine and try to reproduce the Exception error.
??? IF THE EXCEPTION ERROR DOES NOT OCCUR: Congratulations, you're
done! At this time, you may want to remove any unnecessary
troubleshooting parameters from the QEMM386.SYS device line in your
CONFIG.SYS file. Leaving the parameters on the line isn't harmful,
but may be inefficient. To do this, edit the CONFIG.SYS (QEMM's
Manifest utility in the \QEMM directory allows you to easily do
this) and remove the parameters one at a time. Reboot the machine
and try to reproduce the conflict to isolate the parameter that
resolves the conflict. The following parameters are the
troubleshooting parameters added by QSETUP:
DB:2, RH:N, SH:N, TM:N, XBDA:N, TR:N, CF:N, FILL:N, MR:N
Once you have identified the parameter that resolves the conflict,
you may remove the remaining troubleshooting parameters; you are then
finished with this technote.
??? IF THE EXCEPTION ERROR STILL OCCURS: Continue with the next
section, *DISABLE DOS-UP*.
*DISABLE DOS-UP*
QEMM's DOS-UP feature may be involved with your Exception error. From
the \QEMM directory, run the QSETUP program, press the letter "U" to
select "Enable or disable DOS-Up." Press the letter "N" to disable the
DOS-Up feature followed by <Enter> to go back to the QSETUP OPTIONS menu.
Press the letter "S" to "Save configuration and Quit." You will be asked
by QSETUP if you would like to run Optimize. Press <Enter> to begin the
Optimize process. When Optimize has completed, try to recreate the Exception
error.
??? IF THE EXCEPTION ERROR DOES NOT OCCUR: DOS-Up is adding to the
conflict. By partially enabling the DOS-Up feature you can still
receive the benefits of DOS-Up while avoiding the Exception error.
From the QSETUP main menu, press the "U" key to "Enable or disable
DOS-Up," and then the "P" key for a "Partial" DOS-Up configuration.
This brings you to the DOS-Up Options screen, which allows you to
turn on or off the loading high of the 4 parts of DOS.
1 = DOS Resources No
2 = COMMAND.COM No
3 = DOS Data No
H = DOS=HIGH No
Test the system by enabling only one of these options at a time,
saving the configuration, rebooting, and trying to reproduce the
Exception error. Once the option that is causing the
conflict is isolated, setting the option to "No" in QSETUP will
ensure that QEMM's Optimize program will not enable this part of
DOS-Up in the future. You have resolved the conflict and are
finished with this technote.
??? IF THE EXCEPTION ERROR STILL OCCURS: Go to STEP 2.
STEP 2
CLEAN BOOT
----------
In order to ensure that another driver isn't adding to the conflict, you
should temporarily disable those drivers and TSRs not required to boot
the machine or to reproduce the conflict.
Some conflicts require other drivers or TSRs to be loaded in order to
attempt to reproduce the conflict. For example, if the conflict is
related to a CD-ROM, the drivers for the CD-ROM must be loaded. Also note
that if your hard drive is compressed or requires a driver to be loaded
then these drivers should NOT be REMarked out.
Using your favorite editor, edit your CONFIG.SYS file. On every line in
this file (EXCEPT the QEMM386.SYS line and those required to boot the
machine or reproduce the conflict) place the word REM at the beginning of
that line. For example:
DEVICE=C:\QEMM\QEMM386.SYS RAM R:1
REM DOS=HIGH
REM FILES=30
REM BUFFERS=30
REM DEVICE=C:\DOS\ANSI.SYS
Your CONFIG.SYS will have different lines, of course, with different
values on them.
Save this file. Perform the same operation on your AUTOEXEC.BAT file,
adding REM to all lines that are not necessary to recreate the
Exception error (but you MAY leave statements that begin with PATH or
PROMPT). Reboot your system and try to reproduce the Exception error.
??? IF THE EXCEPTION ERROR DOES NOT OCCUR: Remove each of your REMark
statements one at a time from your AUTOEXEC.BAT file, saving and
rebooting after each, to try and recreate the problem. Should the
Exception error occur, the last line you unREMarked is the source of
the problem.
If you have removed the REMs from all the lines in the AUTOEXEC.BAT
file without encountering the error, the problem is in the
CONFIG.SYS file. In that case, repeat the instructions in the
previous paragraph, but perform the steps for the CONFIG.SYS file
this time. Similarly, the last line you unREMarked prior to the
error reappearing is the line responsible for the problem. Go to
the section *RESOLVING CONFLICTS WITH OTHER DRIVERS*.
??? IF THE EXCEPTION ERROR STILL OCCURS: Go to STEP 3.
*RESOLVING CONFLICTS WITH OTHER DRIVERS*
You have isolated the conflict and determined which driver or TSR is
causing it. Contacting the manufacturer of the program is often the
best way to resolve the conflict; however, Quarterdeck Technical
Support has found that the following suggestions resolve many other
programs' incompatibilities:
o Configure the program to NOT use expanded memory. Some programs
misuse expanded memory, and by configuring them to use extended
or conventional memory the conflict with your system may be
avoided. Consult the program's documentation for configuration
options.
o Try loading the program low. Some programs are written with the
assumption that they will be loaded in conventional memory and
fail to function properly when loaded into upper memory.
Programs that load themselves into upper memory should be
tested with this feature disabled.
o Contact the manufacturer of the program to acquire the latest
version of the program. Newer versions may contain
compatibility fixes for known conflicts.
You are finished with this technote.
STEP 3
ELIMINATE HIGH RAM CONFLICTS
----------------------------
To ensure that there is no conflict in upper memory, you should eliminate
all High RAM and test the system. Run QSETUP from the \QEMM directory,
select P, "Review or change QEMM parameters" followed by R, "Fill upper
memory with RAM." You should select "No" to ensure that QEMM will not
create High RAM. Pressing "A" to accept the changes followed by "S" to
save the configuration will allow you to exit QSETUP. Reboot the system
and attempt to reproduce the conflict (ignore any messages about programs
not loading into upper memory, as you have removed all High RAM for this
test).
??? IF THE EXCEPTION ERROR DOES NOT OCCUR: There is a conflict in upper
memory. If you are using a bus-mastering SCSI hard disk controller
(consult the SCSI card's documentation if you are unsure), the
BUS-MAST.TEC technote in the \QEMM\TECHNOTE directory will help you
resolve the conflict. Otherwise, the EXCLUDE.TEC technote in the
\QEMM\TECHNOTE directory will help you resolve the upper memory
conflict. You are finished with this technote.
??? IF THE EXCEPTION ERROR STILL OCCURS: There is no upper memory
conflict. You should proceed to STEP 4.
STEP 4
TEST THE CONFIGURATION WITH DOS'S MEMORY MANAGERS
-------------------------------------------------
In this step, you will try to recreate the conflict without QEMM
installed. If the conflict occurs without QEMM on the system then QEMM
is not involved in the conflict.
Edit your CONFIG.SYS with your favorite text editor, locate the
QEMM386.SYS line, and at the beginning of that line, add the word REM, as
in the example below:
REM DEVICE=C:\QEMM\QEMM386.SYS <additional parameters>
Directly below this line, add the following two lines:
DEVICE=C:\DOS\HIMEM.SYS
DEVICE=C:\DOS\EMM386.EXE ON RAM 2048
These two lines assume that HIMEM.SYS and EMM386.EXE are in the directory
\DOS. If they are in some other directory, replace the word DOS in the
above two lines with the correct directory name. If there are any
eXcludes or Includes on your QEMM386.SYS line that are necessary to boot
the machine, add them to the EMM386.EXE line as well. Save your changes
and reboot the machine. After rebooting, QEMM will NOT be loaded.
Attempt to reproduce the conflict.
??? IF A CONFLICT DOES NOT OCCUR: If you're loading DOS's memory
managers and you have followed every step of this technical note,
then further troubleshooting is required. Contacting our technical
support department is the quickest and easiest way to resolve the
conflict. Please mention that you have followed this technical note
and were instructed by STEP 4 to contact Quarterdeck for additional
troubleshooting steps.
??? IF A CONFLICT STILL OCCURS: QEMM is NOT involved with the conflict;
you are finished with this technote. Since Exception errors will
generally only display with QEMM enabled, the symptoms of a
remaining problem with the DOS memory managers will most likely be a
machine hang. If a conflict still occurs without QEMM loading,
further QEMM troubleshooting will not affect the conflict. You
should consult the documentation that comes with the software that
generated the Exception error with QEMM or causes a hang with HIMEM
and EMM386, or contact the manufacturer of the program.
Our technical support department is easily reached via electronic
channels such as CompuServe (GO QUARTERDECK), Internet (mail
SUPPORT@QDECK.COM or the comp.os.msdos.desqview Usenet newsgroup),
the Quarterdeck BBS (310-314-3227), or fax (310-314-3217). When
contacting Quarterdeck, be sure to fully explain the symptoms of the
conflict and the results of the tests performed while following this
technical note.
You can also call our Technical Support line at 310-392-9701 for
further assistance. When you call, please be at the machine that is
experiencing the conflict.
APPENDIX
OBTAINING THE LATEST QEMM VERSION
---------------------------------
If you currently have a version of QEMM earlier than QEMM 7, you should
upgrade to ensure complete compatibility with all of the latest software
and hardware. Contact the Quarterdeck Upgrade Department at 800-354-3222
or 310-314-3222 for special upgrade pricing. Please note that we give
you a special upgrade price ONLY after you have registered your product!
If you are using QEMM 7 and would like to update your QEMM version to the
latest maintenance release, free update patches are available on
Compuserve (GO QUARTERDECK, LIB 10), the Quarterdeck BBS (310-314-3227),
anonymous FTP (qdeck.com), or BIX (join desqview). The updated version
can also be ordered from Quarterdeck's Customer Service dept
(800-354-3222) for the cost of shipping & handling.
* Copyright (C) 1994 by Quarterdeck Office Systems *
2.5 - Desqview Settings
-----------------------
The most important DESQVIEW SETUP window is "P" for PERFORMANCE.
-------------------------------------------
| Task Processing Time (in Clock Ticks) |
| |
| Foreground: 2 |
| Background: 2 |
| |
| Memory Useage (in K) |
| |
| Common Memory: 20 |
| DOS Buffer for EMS: 5 |
| |
| Optimise Communications: (Y/N) Y |
| Manage printer contention: (Y/N) N |
| |
-------------------------------------------
Processing:
It is important for communication programs to get access to
CPU on a frequent basis, therefore the default DV setting of
Foreground ticks:9 and Background ticks:3 is inappropriate. I would
suggest at a 2 to 2 ratio is a good starting point. The table below may
help to determine what is best for you:?
CPU Foreground Background
----------------------------------
80386 3 3
80486 2 2
Pentium 1 1
Clock tick settings are NOT set in stone. I know for a fact that 18:18
will work on a Pentium without dropping carriers.
Optimize Communications:
This question asks for a YES or NO ANSWER, but in reality will accept a numeric
answer. Optimize Commnications deals with IRQ priority's and has nothing to
do with COM port numbers.
If you answer "Y" to this question then DV assigns a prioriy sequence of
IRQ 2 3 4 5 6 7 8 9 10 11 12 13 14 15 0 1
unless a mouse is detected at IRQ 2 then the prority would be
IRQ 3 4 5 6 7 8 9 10 11 12 13 14 15 0 1 2
If you are only using COM port "1" then you should answer this question with
a "4" this will yield the following IRQ priority list:
IRQ 4 5 6 7 8 9 10 11 12 13 14 15 0 1 2 3
The main thing to note here is that if you were to then start using COM2 or
decide to only use COM2 then you would be in big trouble, because COM2 will
now be down the bottom of the priority list.
For BBS operators using COM1 and COM2 at standard IRQ's I suggest you set
Optimize Comminications (Y/M): to "3", ensuring that COM1 and COM2 both get
High priority service.
Non-Standard IRQ's:
You can optimize Non-standard COM port IRQ's in the exact same way as the
above example. If you have move COM port 1 to IRQ 5 then enter 5 at the
(Y/N): prompt.
If you are using Non-Standard IRQ's you may find the table below helpful
IRQ Typical Owners
--------------------------------------------------
0 Timer
1 Keyboard
2 Mouse
3 COM2 Numerous Add-On Boards
4 COM1
5 LPT2 Network Cards
6 Floppy Diskette Drive
7 LPT1
8 Realtime clock
9 Reserved
10 Reserved CD-ROM Cards Network Cards
11 Reserved
12 Reserved AUX Pointing Device
13 Coprocessor
14 Fixed Disk Drive
15 Reserved
Suggested Non-Standard IRQ's:
I would suggest using 5 9 11 or 12
2.6 - Can you Share Interrupts Under Desqview?
----------------------------------------------
The answer is a Strong 'NO' for Serial Communications.
A number of multiport cards come configure as per the table below:
COM Port IRQ Address
--------------------------
1 4 3F8
2 3 2F8
3 4 3E8
4 3 2E8
From the table you will notice that COM1 & 3 and COM2 & 4 share interrupts,
this will NOT work under Desqview. If you try to run all four ports sharing
IRQ's at least two of the Modems will respond at startup with:
"Modem Not Responding" or "Did Not Receive OK"
or a similar message indicating that your modem isn't responding.
Each COM port needs a unique IRQ, which you can most likely be derived from
the earlier typical IRQ table.
2.7 - Desqview and Port Addressess
----------------------------------
Port addresses are of relevance to most communication programs, if you are
forced to use Non-Standard addresses then this table may help:
COM1 COM2 COM3 COM4
----------------------------
2E0 2E8 2F0 2F8
2C0 2C8 2D0 2D8
280 288 290 298
200 208 210 218
120 128 130 138
100 108 110 118
2.8 - Configuring a Desqview Window to use Serial Ports
-------------------------------------------------------
When you ADD a program to Desqview you are asked to complete STANDARD
information and are given the opportunity to customize ADVANCED settings.
Typical setup screens are as follows:
------------------------------------------------------------------------------
Standard Options
Program Name............: Serial Communications
Keys to Use on Open Menu: C1 Memory Size (in K): 460
Program...: COMMS1.BAT
Parameters:
Directory.: C:\COMMS
Options:
Writes text directly to screen.......: [Y]
Displays graphics information........: [N] (1)
Virtualize text/graphics (Y,N,T).....: [T] (1)
Uses serial ports (Y,N,1,2)..........: [1] (2)
Requires floppy diskette.............: [N]
------------------------------------------------------------------------------
Notes:
(1) Both Items marked with a (1) can be important in the area of
memory management. If you having problems with a program running
under Desqview that does not use graphics, then leaving graphics set OFF
and Virtualize set to T for TEXT can be a good fault finding technique.
(2) Uses Serial Ports is a VERY IMPORTANT question. See the table below
for the best settings:
Port Set to
--------------
COM1 1
COM2 2
COM3 Y
COM4 Y
-----------------------------------------------------------------------------
Advanced Options
System Memory (in K).......: 0 Maximum Program Memory Size (in K):
Script Buffer Size.......: 1000 Maximum EMS/XMS/VCPI/DPMI (in K):
Text Pages: 4 Graphics Pages: 0 Initial Video Mode:
Window Position: ║
Maximum Height: 25 Starting Height: 25 Starting Row...: 0
Maximum Width.: 80 Starting Width.: 80 Starting Column: 0
Shared Program
Pathname..:
Data......:
*Close on exit (Y,N,blank)......: [N] Uses its own colors.............: [Y]
Allow Close Window command.....: [Y] *Runs in background (Y,N,blank)..: [Y]
+Uses math coprocessor..........: [N] =Keyboard conflict (0-F).........: [0]
Share CPU when foreground......: [Y] Share EGA when foreground/zoomed: [Y]
*Can be swapped out (Y,N,blank).: [N] Protection level (0-3)..........: [0]
-----------------------------------------------------------------------------
* Close on exit: NO - If set to yes when running a BBS the corresponding
node will be terminated
* Can be swapped out: NO - if set to yes a BBS node could ne swapped to disk
and therefore terminated
* Runs in Background: NO - Multiple BBS Nodes run in Background sharing the
CPU with the Foreground
+ Its ok! to set uses Math coprocesser to ON. Some Quick Basic and Turbo
Pascal programs require it.
= Explaining Keyboard conflict does beyond the scope of this document,
however it should be noted that a setting of 8 is know to help fix
ill behaved 3270 emulation sessions
3.0 - FIFO Transmit and Receive Trigger Levels
----------------------------------------------
This is relevant for WILDCAT! 4.x and above
If your communications program allows you to customize FIFO transmit
and receive trigger level settings, then you should take advantage of these
facilities:
For Desqview the optimum settings are:
FIFO Receive Trigger Level: 4
FIFO Transmit Trigger Level: 1
These settings are designed to minimise processor activity which will in
turn improve Desqview performance. If you experience difficulties
with file transfers at 28800 bps you may need to set the Receive Trigger
Level to 1.
4.0 - 16450 vs 16550A UARTS
---------------------------
Most users are now aware of the issues surronding the use of the older 16450
UART's. The superior buffering of the 16550A goes a long way towards solving
most COM Port overruns. If your computer does not support replacement UART's
i.e. the UARTS are permantely soldered in place, then perhaps a new serial
interface card may be the best option.
5.0 - Hayes ESP Card
--------------------
I believe the Hayes Communications Accelerator card is a sound product.
However, I have lost count of the number of messages I have seen on the
CIS GO Hayforum threatening to do unspeakable things to the card. In
my opinion most of the problems are a result of users being far too
impatient.
5.1 - Can you use the ESP Card with Desqview?
---------------------------------------------
Desqview will quite happily support two dual-port ESP cards configured
as COM1-COM4.
My suggest card configuration settings are:
Card 1 Card 2
----------------------
COM1 280
COM2 288
COM3 180
COM4 188
On the diskette supplied with the ESP card is a program called ESPCA
which is the DOS configuration program. The following ESPCA.EXE command
will configure all ports with: Port Multiplier: x1, RTS/CTS flow control
and all ports FIFO enabled:
ESPCA P280:1 P288:1 P180:1 P188:1 R280:+ R288:+ R180:+ R188:+ F
You can ofcourse experiment with various port multipliers.
6.0 - DTE Locked Baud Rates
---------------------------
If you have a 28800 bps modem you should lock the DTE speed at least
38400 bps. Don't lock the speed at 19200.
7.0 - Modem Profile
-------------------
Accessible via the AT&V command in TERMINAL Mode
The active modem profile is Important. A typical Hayes Optima 28.8 profile
might look like this:
ACTIVE PROFILE: B0 B76 E0 L2 M1 N1 P Q0 V1 W0 X4 Y0 &A0 &C1 &D2 &G0 &K3 &Q9 &R0
&S0 &T4 &U0 &X0 &Y0 S00:000 S02:043 S03:013 S04:010 S05:008 S06:004 S07:050
S08:004 S09:006 S10:014 S11:090 S12:050 S25:005 S26:001 S36:007 S37:000 S38:020
S46:002 S48:007 S49:064 S50:250 S108:001 S109:4094 S110:002
The Key Settings are:
E0 - Don't ECHO echo characters from the keyboard in command
state
Q0 - Return RESULT CODES
V1 - Display RESULT CODES in words
&C1 - Track presence of CARRIER DETECT signal
&D2 - Monitor DTR
&K3 - Enable RTS/CTS Flow control
&Q9 - Communicate in V.42bis/MNP2-4 error control
S0 - Select RING to auto answer ON
8.0 - Wildcat! Multi-Line Setup?
--------------------------------
The Wildcat! Sysop Guide covers MULTI-LINE operation in some detail so I
don't want to waste too much time on this subject.
There are two key issues:
1. One Node = One DV! Window = One Modem = One Telephone Line
2. Node 0 is the SYSOP Node in Version 4.x not NODE 1
8.1 - Multi-Line Setup Batch Files
----------------------------------
Each DV! window should be linked to a unique CATx.BAT File. i.e. CAT0.BAT,
CAT1.BAT, CAT2.BAT and so on......
Sample Batch Files
CAT0.BAT CAT1.BAT CAT2.BAT CAT3.BAT
@ECHO OFF @ECHO OFF @ECHO OFF @ECHO OFF
:RELOAD :RELOAD :RELOAD :RELOAD
CD\WC4 CD\WC4 CD\WC4 CD\WC4
SET WCNODEID=0 SET WCNODEID=1 SET WCNODEID=2 SET WCNODEID=3
SET WCPORTID=0 SET WCPORTID=1 SET WCPORTID=2 SET WCPORTID=3
WILDCAT WILDCAT SET WCMDM=HAYES SET WCIRQ=11
GOTO RELOAD GOTO RELOAD WILDCAT SET WCMDM=USROB1
GOTO RELOAD WILDCAT
GOTO RELOAD
CAT0.BAT
--------
Note: WCPORTID=0 - Tells Wildcat! to leave the Modem port alone
WCNODEID=0 - Tells Wildcat! that its the SYSOP Node
CAT1.BAT
--------
Note: WCPORTID=1 - Tells Wildcat! to use Serial or Digiport 1 (COM1)
WCNODEID=1 - Tells Wildcat! to set the Node Number to 1
CAT2.BAT
--------
Note: WCPORTID=2 - Tells Wildcat! to use Serial or Digiport 2 (COM2)
WCNODEID=2 - Tells Wildcat! to set the Node Number to 2
WCMDM=HAYES - Tells Wildcat! to look in the \MODEM subdir for
a .MDM File with the name HAYES which has been customize for
the modem being used.
CAT3.BAT
--------
Note: WCPORTID=3 - Tells Wildcat! to use Serial or Digiport 3 (COM3)
WCNODEID=3 - Tells Wildcat! to set the Node Number to 3
WCMDM=USROB1 - Tells Wildcat! to look in the \MODEM subdir for
a .MDM File with the name USROB1 which has been customize for
the modem being used.
SET WCIRQ=11 - Tells Wildcat! that the default share interupt 4
is NOT to be used (remember we cannot share Interupts) instead
we are using IRQ 11 in this example.
Use the example above to configure your system to your needs. Try Not to
use non stardard BASE I/O Addressess
8.2 - Wildcat .MDM Files
------------------------
You can modify the .MDM modem profile files that come with Wildcat!
using the MSI supplied WCMODEM program.
A typical .MDM File Looks like this:
┌──────────────────────────────────────────────────────────────────────────────┐
│ wcMODEM Copyright (c) 1991,94 Mustang Software, Inc. Version 4.01 MP │
└╔═══════════════════════════ View/Edit MDM Files ═══════════════════════════╗─┘
▒║ Modem name : Hayes Optima 28.8 ▒▒
▒║ Type of serial port : Serial port ▓▒▒
▒║ Communication port number : 1 ░▒▒
▒║ Communication port IRQ : 4 ░▒▒
▒║ Communication port base address : $03F8 ░▒▒
▒║ Determine ringing using : Ring Detect ░▒▒
▒║ Determine baud rate using : Result Code 1 ░▒▒
▒║ Initialize port at what baud rate : 38400 ░▒▒
▒║ Lock DTE at initialization baud rate : Y ░▒▒
▒║ Use CTS/RTS flow control : Y ░▒▒
▒║ Take modem off hook on exit (busy line) : N ░▒▒
▒║ Number of seconds to wait for carrier : 60 ░▒▒
▒║ Milliseconds before answering : 1000 ░▒▒
▒║ Milliseconds to lower DTR for hangup : 2000 ░▒▒
▒║ Milliseconds to delay before prelog : 1000 ░▒▒
▒║ Milliseconds to wait for result code : 3800 ▒▒
▒╟───────────────────────────────────────────────────────────────────────────╢▒▒
▒║ F2 Pick F3 Load F4 Save F10 Done ║▒▒
▒╚═══════════════════════════════════════════════════════════════════════════╝▒▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
Port is CLOSED │ Port #: 1 │ Base Address: 03F8 │ Port Irq: 4 │ Speed: 9600
┌──────────────────────────────────────────────────────────────────────────────┐
│ wcMODEM Copyright (c) 1991,94 Mustang Software, Inc. Version 4.01 MP │
└╔═══════════════════════════ View/Edit MDM Files ═══════════════════════════╗─┘
▒║ Milliseconds between command strings : 2000 ▒▒
▒║ Trigger level for receive FIFO : 4 ░▒▒
▒║ Trigger level for transmit FIFO : 1 ░▒▒
▒║ Verbal code for RING : RING ░▒▒
▒║ Modem reset string : ATZ ▓▒▒
▒║ Modem error correction strings : V.42|MNP2-4|REL|ARQ ░▒▒
▒║ Modem on hook string (ready for calls) : ATH0 ░▒▒
▒║ Modem off hook string (busy) : ATH1 ░▒▒
▒║ Modem initialization string : ATE0V1&C1&D2S95=3S0=0S7=60 ░▒▒
▒║ Modem answer string : ATA ░▒▒
▒║ Modem caller ID string : ░▒▒
▒║────────────────────────── Modem Nram settings ──────────────────────────░▒▒
▒║ Modem reset command : ░▒▒
▒║ Modem setup string # 1 : ░▒▒
▒║ Modem setup string # 2 : ░▒▒
▒║ Modem setup string # 3 : ▒▒
▒╟───────────────────────────────────────────────────────────────────────────╢▒▒
▒║ F2 Pick F3 Load F4 Save F10 Done ║▒▒
▒╚═══════════════════════════════════════════════════════════════════════════╝▒▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
Port is CLOSED │ Port #: 1 │ Base Address: 03F8 │ Port Irq: 4 │ Speed: 38400
*** PAGE #1 - IMPORTANT SETTINGS ***
Type of serial port : Serial port
Communication port number : 1
Communication port IRQ : 4
Communication port base address : $03F8
Determine ringing using : Ring Detect
Determine baud rate using : Result Code 1
Initialize port at what baud rate : 38400
Lock DTE at initialization baud rate : Y
Use CTS/RTS flow control : Y
******************************
port IRQ - Should be matched on the physical port or Multi-port I/O Board
base add - Should be matched on the physical port or Multi-port I/O Board
Determine Ringing Using: Ring Detect: Signal From Modem RI Circuit
Ring Result: Uses the Modem Result Code
Auto Answer: Modem does all the work via ATS0=0
Determine Baud Rate Using: Result Code 1: Monitor CD while waiting for Connect String
Result Code 2: Don't Monitor while waiting
CR: Use the old style PRESS CR a few times method
DTE Assume calls is at Locked DTE Rate
*** PAGE #2 - IMPORTANT SETTINGS ***
Trigger level for receive FIFO : 4
Trigger level for transmit FIFO : 1
Verbal code for RING : RING
Modem reset string : ATZ
Modem error correction strings : V.42|MNP2-4|REL|ARQ
Modem on hook string (ready for calls) : ATH0
Modem off hook string (busy) : ATH1
Modem initialization string : ATE0V1&C1&D2S95=3S0=0S7=60
****************************
FIFO Trigger Levels: See Section 3.0
Modem Error Correction Strings: Match these with your modem manual
On & OFF Strings: These are correct for the Hayes 28.8.
v4.00 of Wildcat! stated them incurrectly
Modem Init String: See Section 7.0
9.0 - Wildcat! Upload and DownLoad Failures
-------------------------------------------
The are alot of users still asking about file transfer failures which manifest
themselves in two main ways:
1. Excessive CRC errors
2. Link seems to run ok! for around 120K or so then dies dropping back
and eventually losing carrier.
I have experience both!
9.1 - Poor Quality Phone Lines
------------------------------
There is NO doubt that a poor quality phone line can cause the two problems
nentioned above to occur. Ask you local telephone company to check the lines
for you.
Assuming that your problems are being caused by line noise or interference you
might like to try the following:
1. Get hold of a Noise testing program and run it on your BBS and see
what degree of noise the program picks up,
2. Make sure your BBS lines do NOT have more than three Ring Equivilent
devices attached to them.
3. Disconnect any membrain style handsets from your modem line and retest
them.
Try and determine where your street distribution box is for the telephone lines
that run into your home or office. If your lines are pole based look for a
pole with a bunch of wires all descending together towards the ground. If
you have underground lines look for a lockable waist height pilar and note
its location relative to your home.
If your street distribution point is a dozen or so houses or average sized
blocks of land away, then chances are your in for trouble with little
hope of fault resolution.
9.2 - File Transfer Failure Hardware Factors
--------------------------------------------
Always check the obvious:
1. Check your installation by using a different brand of modem
2. Check all phsyical connections.
3. Check all environmental facts, such as heat, cold or dirty power
supply.
9.3 - File Transfer Failure Software Factors
--------------------------------------------
If you are certain that your Telephone Lines are Fine and that your modem is
fuctioning correctly then the port of last resort is software.
Here are some things to try:
1. Carefully review your modems NRAM settings for data compression, if
in doubt use AT&F to restore your modem to its factory ready state.
2. Carefully review your modems NRAM settings for error correction, if
in doubt use AT&F to restore your modem to its factory ready state.
3. Don't be frightended to play with items 1 or 2.
4. Remove any vsheild style programs from your boot up files
5. In MAKEWILD under Memory and Hardware Information set the Following:
Size of Scollback Buffer (in K): 5
Where Should Overlay be Held: Disk
Extra Memory in K for overlay Buffer: 0
Where should swapped data be held: EMS
6. If your PC uses SHADOW memory of any type disable it in CMOS some
users have claimed it can cause problems.
7. Discontinue the use of Desqview, Qemm, DOS Share, EMM386, Smartdrv
and run Wildcat as a SINGLE LINE DOS System.
Use STARTUP batch files similar to these:
AUTOEXEC.BAT
------------
@ECHO OFF
PROMPT=$P$G
PATH=C:\;\DOS;\WILDCAT;
SET WCPORTID=1
SET WCNODEID=1
CD\WILDCAT
WILDCAT
CONFIG.SYS
----------
DEVICE = C:\DOS\HIMEM.SYS /TESTMEM:OFF
DOS = HIGH
FILES = 80
BUFFERS = 30
NUMLOCK = OFF
SHELL = \DOS\COMMAND.COM C:\DOS\ /E:2048 /p
10.0 - Summary
--------------
This is the first PUBLIC release of this file. It is not yet complete and
will be added to on an ongoing basis. WATCH for updates.
11.0 - Contacting Me
--------------------
I am happy to answer any questions that you may have. I carry MSI SupportNet
so a message left in any of the [E] conferences will reach me.
Michael Purdy
(Sysop) The Speed Limit BBS
Melbourne, Australia +61 3 331 2543
Internet:100026,1177@Compuserve.com